Address memory exhaustion errors within performance testing workflow#11930
Address memory exhaustion errors within performance testing workflow#11930desrosj wants to merge 6 commits into
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
desrosj
requested review from
Copilot,
johnbillion,
mukeshpanchal27,
swissspidy and
westonruter
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull request overview
This PR updates the reusable performance testing workflow to avoid memory exhaustion when running baseline (subject: base) measurements against WordPress versions newer than 6.7.0 by downloading the baseline WordPress version using WP‑CLI on the GitHub Actions runner (instead of invoking WP‑CLI inside the Docker environment).
Changes:
- Adds a conditional
setup-phpstep (base-only) to install WP‑CLI on the runner. - Replaces
npm run env:cli -- core download ...with a directwp core download ...call for the baseline setup.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
desrosj
force-pushed
the
fix/performance-testing-exhaustion
branch
from
27e0a21 to
b605216
Compare
This attempts to address memory exhaustion errors that have been happening any time the
BASE_TAGwithin the performance testing workflow is set to any value higher than6.7.0by downloading the needed version of WordPress using WP-CLI inside the GitHub Actions runner instead of within the Docker environment.7.0.0.Trac ticket: Core-65289.
Use of AI Tools
None
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.